Minor doc tweaks.

diff --git a/filter_skeleton.c b/filter_skeleton.c
index c3bea639032f8e2a03fb63050f667ecfdb97cc54..8c5651af7dca466387a740803acf59fd152f6b14 100644 (file)
--- a/filter_skeleton.c
+++ b/filter_skeleton.c
@@ -32,6 +32,7 @@
 
 #define MYNAME "filter_skeleton"
 
+#if FILTERS_ENABLED
 
 // Any arg in this list will appear in command line help and will be 
 // populated for you.
@@ -103,3 +104,4 @@ filter_vecs_t filter_skeleton_vecs = {
 };
 
 /*******************************************************************************/
+#endif // FILTERS_ENABLED

diff --git a/xmldoc/filters/transform.xml b/xmldoc/filters/transform.xml
index 76202cda677f0ca7c36dfb9db75971ebd91839ba..87a87d2e098107ef5932e3a9e82f5a47765f4d11 100644 (file)
--- a/xmldoc/filters/transform.xml
+++ b/xmldoc/filters/transform.xml
@@ -2,13 +2,10 @@
   This filter can be used to convert GPS data between different data types.
 </para>
 <para>
-  Not all known and unknown GPS data formats has beed designed on
-  one common idea. So we have waypoint-only, route-only, track-only
-  and formats containing more than one of them.
-</para>
-<para>
-  To bring such different formats together we've implemented the transform 
-  filter. 
+  Some GPS data formats support only some subset of waypoints, tracks,
+  and routes.  The transform filter allows you to convert between these
+  types.  For example, it can be used to convert a pile of waypoints (such
+  as those from a CSV file) into a track or vice versa.
 </para>
 <para>
   The following example show you how to create a route from a waypoint table.